What

Fixes a bug reported by QA where authenticator app secret keys were not displayed following a validation error.

The fix ensures the secret will display both:

• where the code format is invalid and therefore fails the validation rules as set in setup-authenticator-app-validation.ts
• where the code is incorrect, as demonstrated by the verifyMfaCode service not returning a success

The related integration tests have also been updated to prevent assertions passing where the code is not included (the previous non-empty test would always pass because the text included whitespace and line break characters)

How to review

1. Code Review
2. Run this branch locally
3. Go through an account creation journey choosing authenticator app when asked to choose a method for second factor.
4. On the "Set up an authenticator app" screen confirm that the secret key can be seen when expanding "I cannot scan the QR code"
5. Confirm that the secret key is still included in error states when you submit different permutations of invalid formats. This includes: not entering a code; entering a code that is too long; entering a six digit code that contains a letter
6. Confirm that the secret key is still included when you enter a valid code that is incorrect.
7. Confirm that a correct code can be submitted